| Package | ForgePatientChart.0830 |
| Type | StructureDefinition |
| Id | Id |
| FHIR Version | R4 |
| Source | https://simplifier.net/resolve?scope=ForgePatientChart.0830@0.1.0&canonical=http://telus.com/fhir/patientChart/StructureDefinition/ext-patient-sexForClinicaUse |
| Url | http://telus.com/fhir/patientChart/StructureDefinition/ext-patient-sexForClinicaUse |
| Version | 4.0.1 |
| Status | draft |
| Date | 2022-01-24T16:55:11+11:00 |
| Name | SexForClinicalUse |
| Title | sexForClinicalUse |
| Experimental | False |
| Authority | hl7 |
| Description | **Sex for Clinical Use (SFCU) Overview** Sex for Clinical Use is a categorization of sex derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc. This property is intended for use in clinical decision making and indicates that treatment or diagnostic tests should consider best practices associated with the relevant reference population. While clinical decision-making processes could account for the specific physiological or anatomical attributes of the patient, there are several practical considerations, such as patient privacy and limited capabilities of existing systems which create the need for a categorization that is easy to exchange. The Sex for Clinical Use categorization is intended to bridge the gap between the hypothetical ideal and the practical needs of operational systems. **Sex for Clinical Use (SFCU) Contexts** Sex for Clinical Use is a contextual concept. For example, a patient may generally be categorized as male, but for a specific lab test, the resulting lab should use the reference ranges associated with a female reference population. In this case, systems may provide a patient-context [sexForClinicalUse](extension-patient-sexforclinicaluse.html) that acts as a 'default' for most care and annotate the lab order with a context-specific sexForClinicalUse. Systems may determine what enclosing contexts are useful, but Patient, Encounter and EpisodeOfCare are three enclosing contexts that may often apply. The [sexForClinicalUse](extension-patient-sexforclinicaluse.html) extension can be used to communicate a clinical sex category on the on relevant clinical resources (e.g., DiagnosticReport , ServiceRequest) or enclosing contexts (e.g., Patient, Encounter, EpisodeOfCare). **Sex for Clinical Use (SFCU) Categorization** For ease of interoperability, a patient’s sex for clinical use is constrained to four possible categories. Any patient for which special considerations apply should be categorized as 'Specified'. The 'Specified' category is often represented as 'Other' in existing systems. **Female** - Available data indicates that diagnostics, analytics, and treatments should consider best practices associated with female reference populations. **Male** - Available data indicates that diagnostics, analytics, and treatments should consider best practices associated with male reference populations. **Specified** - Available data indicates that diagnostics, analytics, and treatment best practices may be undefined or not aligned with existing sex-derived reference populations. Individuals or systems providing care should either use default behavior that is safe for both male and female populations, individually review treatment options with the patient, or carefully inspect relevant observations before proceeding with treatment. **Unknown** - The sex for clinical use cannot be determined because there are no relevant evidence or documentation, or the evidence or documentation are not sufficient to determine a value. **Sex for Clinical Use (SFCU) History and Practices** Prior to the definition of Sex for Clinical Use as a concept, systems may have used administrative gender as an approximation of patient-level sex for clinical use. This practice required pre-coordination among exchange parters to explicitly overload the administrative sex concept for use as a clinical sex concept. In cases where there was no pre-coordination, some systems may have incorrectly inferred information about a patient's clinical sex from administrative gender. In the context of ordering workflows, systems may use Ask at Order Entry (AOE) questions to collect concepts similar to sex for clinical use. |
| Type | Extension |
| Kind | complex-type |
No resources found
No resources found
FHIR{
"resourceType" : "StructureDefinition",
"id" : "patient-sexForClinicalUse",
"extension" : [
{
"url" : "http://telus.com/fhir/patientChart/StructureDefinition/patient-sexForClinicalUse"
}
],
"url" : "http://telus.com/fhir/patientChart/StructureDefinition/ext-patient-sexForClinicaUse",
"version" : "4.0.1",
"name" : "SexForClinicalUse",
"title" : "sexForClinicalUse",
"status" : "draft",
"experimental" : false,
"date" : "2022-01-24T16:55:11+11:00",
"publisher" : "HL7",
"description" : "**Sex for Clinical Use (SFCU) Overview** Sex for Clinical Use is a categorization of sex derived from observable information such as an organ inventory, recent hormone lab tests, genetic testing, menstrual status, obstetric history, etc. This property is intended for use in clinical decision making and indicates that treatment or diagnostic tests should consider best practices associated with the relevant reference population. While clinical decision-making processes could account for the specific physiological or anatomical attributes of the patient, there are several practical considerations, such as patient privacy and limited capabilities of existing systems which create the need for a categorization that is easy to exchange. The Sex for Clinical Use categorization is intended to bridge the gap between the hypothetical ideal and the practical needs of operational systems. **Sex for Clinical Use (SFCU) Contexts** Sex for Clinical Use is a contextual concept. For example, a patient may generally be categorized as male, but for a specific lab test, the resulting lab should use the reference ranges associated with a female reference population. In this case, systems may provide a patient-context [sexForClinicalUse](extension-patient-sexforclinicaluse.html) that acts as a 'default' for most care and annotate the lab order with a context-specific sexForClinicalUse. Systems may determine what enclosing contexts are useful, but Patient, Encounter and EpisodeOfCare are three enclosing contexts that may often apply. The [sexForClinicalUse](extension-patient-sexforclinicaluse.html) extension can be used to communicate a clinical sex category on the on relevant clinical resources (e.g., DiagnosticReport , ServiceRequest) or enclosing contexts (e.g., Patient, Encounter, EpisodeOfCare). **Sex for Clinical Use (SFCU) Categorization** For ease of interoperability, a patient’s sex for clinical use is constrained to four possible categories. Any patient for which special considerations apply should be categorized as 'Specified'. The 'Specified' category is often represented as 'Other' in existing systems. **Female** - Available data indicates that diagnostics, analytics, and treatments should consider best practices associated with female reference populations. **Male** - Available data indicates that diagnostics, analytics, and treatments should consider best practices associated with male reference populations. **Specified** - Available data indicates that diagnostics, analytics, and treatment best practices may be undefined or not aligned with existing sex-derived reference populations. Individuals or systems providing care should either use default behavior that is safe for both male and female populations, individually review treatment options with the patient, or carefully inspect relevant observations before proceeding with treatment. **Unknown** - The sex for clinical use cannot be determined because there are no relevant evidence or documentation, or the evidence or documentation are not sufficient to determine a value. **Sex for Clinical Use (SFCU) History and Practices** Prior to the definition of Sex for Clinical Use as a concept, systems may have used administrative gender as an approximation of patient-level sex for clinical use. This practice required pre-coordination among exchange parters to explicitly overload the administrative sex concept for use as a clinical sex concept. In cases where there was no pre-coordination, some systems may have incorrectly inferred information about a patient's clinical sex from administrative gender. In the context of ordering workflows, systems may use Ask at Order Entry (AOE) questions to collect concepts similar to sex for clinical use.",
"fhirVersion" : "4.0.1",
"mapping" : [
{
"identity" : "rim",
"uri" : "http://hl7.org/v3",
"name" : "RIM Mapping"
}
],
"kind" : "complex-type",
"abstract" : false,
"context" : [
{
"type" : "element",
"expression" : "Resource"
}
],
"type" : "Extension",
"baseDefinition" : "http://hl7.org/fhir/StructureDefinition/Extension",
"derivation" : "constraint",
"differential" : {
"element" : [
{
"id" : "Extension",
"path" : "Extension",
"short" : "A context-specific sex for clinical use",
"definition" : "A context-specific categorization of a patient's sex for the purpose of clinical use",
"comment" : "Usage Note: This may be added to any resource where it is necessary to specify the Sex for Clinical Use. For example, on a lab order, lab result or service request. This is not supported currently by EMRs but is included as it is expected to be supported in the near future.\r\n\r\nAlignment: This is a pre-adoption of an R5 HL7 extension. This is published as a TELUS extension and implementers will need to update the URL in the future. The datatype on supportingInfo has been changed to a codeableConcept in order to be compliant with R4; it is not supported at this time."
},
{
"id" : "Extension.extension",
"path" : "Extension.extension",
"slicing" : {
"discriminator" : [
{
"type" : "value",
"path" : "url"
}
],
"rules" : "open"
},
"min" : 1
},
{
"id" : "Extension.extension:value",
"path" : "Extension.extension",
"sliceName" : "value",
"short" : "A context-specific sex for clinical use",
"definition" : "A context-specific categorization of a patient's sex for the purpose of clinical use",
"comment" : "Sex for clinical use may be contexual. For example, the sex for clinical use for mammogram health maintenance may by different than the sex for clinical use for the purpose of selecting a reference range for a lab test. There may also be a patient-context sex for clinical use that is a general categorization that would apply across all contexts if more specific information is not available.",
"min" : 1,
"max" : "1",
"mustSupport" : true
},
{
"id" : "Extension.extension:value.url",
"path" : "Extension.extension.url",
"type" : [
{
"code" : "uri"
}
],
"fixedUri" : "value"
},
{
"id" : "Extension.extension:value.value[x]",
"path" : "Extension.extension.value[x]",
"min" : 1,
"type" : [
{
"code" : "CodeableConcept"
}
],
"binding" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/elementdefinition-bindingName",
"valueString" : "sexForClinicalUse"
}
],
"strength" : "required",
"valueSet" : "http://hl7.org/fhir/ValueSet/sex-for-clinical-use"
}
},
{
"id" : "Extension.extension:period",
"path" : "Extension.extension",
"sliceName" : "period",
"short" : "When the sex for clinical use applies",
"definition" : "The time period during which the sex for clinical use applies to the patient",
"min" : 0,
"max" : "1",
"mustSupport" : true
},
{
"id" : "Extension.extension:period.url",
"path" : "Extension.extension.url",
"type" : [
{
"code" : "uri"
}
],
"fixedUri" : "period"
},
{
"id" : "Extension.extension:period.value[x]",
"path" : "Extension.extension.value[x]",
"min" : 1,
"type" : [
{
"code" : "Period"
}
]
},
{
"id" : "Extension.extension:comment",
"path" : "Extension.extension",
"sliceName" : "comment",
"short" : "Context about the sex for clinical use",
"definition" : "Further explanation about the context for the sex for clinical use",
"min" : 0,
"max" : "1",
"mustSupport" : true
},
{
"id" : "Extension.extension:comment.url",
"path" : "Extension.extension.url",
"type" : [
{
"code" : "uri"
}
],
"fixedUri" : "comment"
},
{
"id" : "Extension.extension:comment.value[x]",
"path" : "Extension.extension.value[x]",
"min" : 1,
"type" : [
{
"code" : "string"
}
]
},
{
"id" : "Extension.extension:supportingInfo",
"path" : "Extension.extension",
"sliceName" : "supportingInfo",
"short" : "Source of the sex for clincal use",
"definition" : "Other clinical evidence or documentation that was used to determine the sex for clincal use",
"comment" : "For example, a patient with an initial diagnosis of an intersex condition could have supporting clinical observations specific to the diagnosis. Additional information may be provided in the comment attribute.",
"min" : 0
},
{
"id" : "Extension.extension:supportingInfo.url",
"path" : "Extension.extension.url",
"type" : [
{
"code" : "uri"
}
],
"fixedUri" : "supportingInfo"
},
{
"id" : "Extension.extension:supportingInfo.value[x]",
"path" : "Extension.extension.value[x]",
"min" : 1,
"type" : [
{
"code" : "CodeableConcept"
}
]
},
{
"id" : "Extension.url",
"path" : "Extension.url",
"fixedUri" : "http://telus.com/fhir/patientChart/StructureDefinition/patient-sexForClinicalUse"
},
{
"id" : "Extension.value[x]",
"path" : "Extension.value[x]",
"max" : "0"
}
]
},
"text" : {
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.